The World of Computer Software/The World of Computer Software.iso/wwcp120.zip/RULES.DOC

Text File | 1992-04-21 | 31KB | 601 lines

                        WWIVnet Policies and Information

            (excerpted from _WWIVnet Docs v2.29_ by Wig De Moville)



  ORGANIZATION

       WWIVnet originally began in 1988 with 25 charter members who helped
  Wayne Bell develop the network software and debug it.  Since that time
  it has spread from a small Los Angeles-based system of local boards to
  an international network.  Currently, the network software is in its
  29th version although there will undoubtedly be many future versions
  written as well.  These versions are referred to as Net1, Net2,...Net20,
  etc.  The international network has Wayne Bell as its head.  The network
  is organized into groups with each group having a Group Coordinator.
  Currently there are 12 groups.  Each group is composed of approximately
  50 systems which may be located in one or more area codes.  Each area
  code where there are more than 5 network systems has its own Area
  Coordinator.

       For those area that have fewer than 5 systems, the Group
  Coordinator functions as the area coordinator for the small area code.

       An understanding of the roles of the Group Coordinator and Area
  Coordinator facilitates cooperation and prevents arguments and disputes.
  The rules, regulations and suggestions which are presented here are
  designed to insure that the network functions well and that friction
  between the components of WWIVnet does not develop.

       However, these rules should not be forced to apply to situations
  where they do not seem to logically fit.  Instead, the rules can be
  adapted to the situation.  These rules should not be regarded as "carved
  in stone," for WWIVnet is dynamic and undergoing evolutionary changes as
  it grows.  These documents will be revised from time to time to reflect
  these changes.


 Group Coordinator

       The group coordinator is a position developed by Wayne in response
  to growth in the network and suggestions of many interested parties.
  The network growth necessitated a division of duties so that the
  updating of the network could occur in smaller packages; that is, there
  was up through NET19 a natural limit of 32k to the length of
  BBSLIST.NET.  As the number of systems grew and the length of the file
  approached its natural limit, Wayne was faced with the decision of
  either developing a new organizational structure or telling network
  members that no new systems could be added.  For obvious reasons, the
  first alternative was selected.

       In addition to serving as the Area Coordinator for area codes where
  there are five or fewer systems, the Group Coordinator has the following
  duties:

       1)   Receive from AC's and forward to Wayne Bell updates to the
            BBSLIST.NET (i.e., information on systems being added to the
            network).  Plans have been made to allow distribution to group
            members directly from the GC but this is not taking place yet.

       2)   Send out CONNECT.NET entries to the member systems of the
            group.  The current files, called CONNECT.0 to CONNECT.12, are
            distributed by Wayne Bell, the Net Coordinator (NC), but in
            the future the CONNECT file for each group may also be
            distributed to the members of a group by the GC.

       3)   Help determine the best routing for out-of-group messages.

       4)   Help to insure that no system or group of systems becomes
            isolated (i.e., without a connection to the outside world).

       5)   Serve as first step in grievances between sysops and their
            Area Coordinators and in other disputes.  The final step is to
            have Wayne Bell resolve the problem.

       6)   Facilitate the election process when Area Codes hold AC
            elections.

       The duties listed above are discussed indirectly in more detail in
  connection with the technical working of the network.


Area Coordinator

       The duties of an Area Coordinator are simple and few; however,
  these activities are extremely important for the proper functioning of
  WWIVnet.  The duties are as follows:

       1)   Investigate net applicants and either assign them a node
            number or provide them with a reason why no node number is
            being assigned.  This function is discussed more thoroughly
            under rules and regulations below.

       2)   Forward the information to the Group Coordinator.

       3)   Process changes, new connection requests, etc., for sysops in
            the area code.


       These duties and other services that might be rendered by an area
  coordinator are further discussed in the section on rules and
  regulations and in the section on the technical working of the network.

RULES AND REGULATIONS

       WWIVnet is characterized by very few rules and regulations.  Those
  that do exist are either absolutely necessary to the proper functioning
  of the network or are common courtesies that should be extended between
  cooperating systems.  I will use rule and regulation interchangeably in
  the discussion which follows.  There is no difference between the terms
  as used here.  I have done my best to organize these rules in terms of
  whom they apply to.  Since every AC or GC is also a Sysop, the rules for
  Sysops apply equally to the AC's and GC'S.


Requirements for GC

       The person serving as GC was either (a) nominated by Wayne Bell or
  someone else such as an AC or (b) self nominated due to the connections
  maintained.  The individual has been accepted by Wayne, by the AC's with
  whom he/she must relate, and possibly by a vote of the sysops in the
  area as well.  However, the process of becoming a GC is NOT necessarily
  a democratic one.  That is, being a Group Coordinator is not the result
  of a popularity contest; instead, it is the result of demonstrated
  maturity in the network, willingness to serve, and having the confidence
  of the AC's and Wayne Bell.  Such an individual should be mature (not
  necessarily old), easy to get along with, prompt in answering to the
  needs of others, and be willing to devote time to insuring that the
  group is well represented.  [Side Note: The he/she construction above
  seems to be unnecessarily awkward; therefore, where the use of a pronoun
  seems appropriate, I shall use either he or she; however, the context
  should make the pronoun's referent clear.  The gender of the person(s)
  referred to does not really matter.]

       The Group Coordinator should agree to the following conditions:

       1)   She will serve as long as she maintains the confidence of
            those being served and as long as she is willing.  However,
            this period of service should be a minimum of three months,
            and she must provide at least 3 weeks notice before stepping
            down from the position.

       2)   He will maintain contact with the AC's and Sysops within the
            area in order to insure that (a) all boards are receiving net
            messages and net updates, (b) no board or group of boards
            becomes cut-off from the rest of the network.

       3)   She will listen to both sides of any disagreement and promote
            communication between the parties involved in the dispute.
            She will render an impartial recommendation based upon the
            facts and inform Wayne Bell of the dispute and recommended
            resolution in those instances where it appears that people may
            have strong and/or hurt feelings.  This role calls for some
            maturity and judgement.  Wayne should not be informed or
            bothered with the settlement of a dispute regarding a trivial
            matter, but he should be informed about all disputes which
            might have an unsettling effect upon the network.

       4)   Promptness, Accuracy, Honesty, and Communications should be
            the qualities promoted by the Group Coordinator.  The workings
            of the group (actually a mini-network) depend upon the Group
            Coordinator's being prompt in his responses, accurate in her
            work, honest in his dealings with others, and demonstrative of
            a willingness to communicate in an open and frank manner but
            with tact where it is called for.

       5)   He will appoint an Emergency or Assistant GC.  The identity of
            the appointee will be made known to the NC.  The assistant
            should obtain an account on Amber (the NC's board).  If an
            emergency situation should arise or the GC go on an extended
            vacation, then the Assistant could be given access to the GC
            software and make network updates until the GC is able to
            return to his position.  The Assistant is NOT automatically in
            line for the GC position.  He might or might not be appointed
            as GC in the event that a replacement situation evolved.

       The role of Group Coordinator may evolve in the future to take on
  additional responsibilities and there may be additional requirements.


Requirements for AC

       Prerequisites to be an Area Coordinator.  To be an area
  coordinator, you must meet the following criteria:

       1)   Be currently running a system 24 hours a day.
       2)   Promise to run the system for at least 3 months into the
            future.
       3)   Promise to notify the GC at least 2 weeks in advance of taking
            down your system, and suggest a new coordinator for your area
            if/when you do.
       4)   Be willing to put in some time to get the net up and keep it
            going.
       5)   Be willing to rack up some LD charges, or know someone in your
            area who is.
  (WWIVnet Guide by Will Daystrom (c) White Starline Software)


       If there is no AC in your area, you may confer with your GC who
  will help the boards in your area (once there are more than five) obtain
  an AC.  Currently several methods exist in WWIVnet for the establishment
  of an AC in an area where there is none or where the previous AC left
  without recommending a replacement.  These methods include: (1)
  nomination of an AC by the GC and ratification/refusal by the sysops in
  the area code; (2) nomination of an AC by the sysops in the area code
  and ratification/refusal by the GC.  In any case, once an AC has been
  chosen for the area, Wayne Bell must still approve that person's acting
  as AC.

       It should be obvious from the guidelines in this manual, that the
  AC performs a valuable but somewhat thankless function and that there is
  no power associated with the position.  Therefore, to attempt a coup in
  order to become AC would be somewhat meaningless.  If an AC has power,
  it is because area boards have permitted the person to have power, NOT
  because the AC position is powerful.


       If the number of boards in an area that has an AC drops below five,
  the AC continues to function.  The GC does not take over the
  responsibilities of AC unless the AC resigns.  In that event, if there
  are fewer than five boards remaining in the area, the GC may fulfill the
  AC's duties until growth brings the number of systems to six or more.


       "There is one (and only one) coordinator per area code, and
       is/her primary duties are to assign net numbers to new systems
       joining the net, accept and check out connection info supplied
       by systems within their area code, and to forward this
       information (connection and bbs info changes) to @1."
       (WWIVnet Guide by Will Daystrom, (c) 1989 White Star Line
       Software)

       The quote above taken from WWIVnet Guide summarizes the primary
  duties of an AC very well.  The only change in the description is that
  now the information is forwarded to the GC who in turn forwards it to 1
  @1.   As an AC you must assign net numbers to new systems that want to
  join the net.  Before assigning the node number, you should establish
  that the board is a viable board.  Basically this means that you must
  feel relatively confident that the applicant will continue to run for a
  few months.  This is necessary in order to insure stability for the
  network.  This information, of course, must be forwarded to the GC.


       In addition to that primary duty, the WWIVnet Guide indicates that
  the area coordinator may under certain circumstances deny a network node
  number to a board.  This should only be done in circumstances which are
  well-defined.

       These are: (1) if the AC has doubts about the stability of the
  board, or (2) the AC has a policy that no part-time boards will be
  permitted in the network.

       In the first case, the AC should inform the sysop that he needs to
  be running for a specified period before a network connection is
  established.  If at that point, there are still concerns about the
  board's stability, the board could be assigned a node number and limited
  to one connection.  The key thing here is communication with the
  applicant.  Be certain that the sysop understands why he cannot get a
  node number immediately, that he is aware of when he will be assigned
  one and under what conditions.

       In the second case, the AC may deny access to the network on a more
  permanent basis, but again, communication is the key to handling the
  situation.  Before adopting a policy the AC would be well-advised to
  discuss it with the GC and with the WWIVnet Sysops of the area code.


Long Distance Connections

       It is NOT the AC's responsibility to establish long distance
  connections for the boards in the area code.  That responsibility
  belongs to the sysop of each board.  In many cases, however, several
  boards will use the long distance connections of one board which acts as
  a hub and which does most of the long distance polling.  In that event,
  the long distance connection may limit the numbers of subs or mail sent
  by those which connect to him.  Note that this is a function of the long
  distance connection and not a function of the AC (even if both are the
  same person).

       As AC you may suggest that certain boards might wish to help
  another with long distance charges and so forth but remember that this
  is purely voluntary.  Also you should remember that you do not have the
  power to prohibit a person from making long distance connections or from
  taking certain subs.  A sysop may make whatever long distance
  connections that he feels that he can afford and may carry any subs that
  he is willing to pay the long distance bill for.  In cases where one
  board makes the long distance connections to obtain subs for others, the
  sysop of the board making the calls may limit the traffic, but that is
  him functioning as long distance connector not as AC.


       Further, the AC is not expected to provide technical advice
  regarding WWIVnet.  It is nice if he can do so, but it is not part of
  the "job description."  There are WWIV SUPPORT BOARDS which should be
  able to provide such advice if it is necessary.


Providing More Services

       An AC may choose to provide additional services to the area.  For
  example, the AC may be instrumental in organizing meetings of local
  and/or area sysops and may help to organize the area for more effect
  long distance connections; however, this is not part of his function as
  an AC and should not be considered as part of the AC's authority.  Any
  arrangements of this kind are accepted by area boards because they
  voluntarily choose to do so.

       They (the area boards) may at any time choose to do things
  differently and it should not affect the AC's duties.  Thus, a word of
  caution to the AC, DO NOT BECOME EGO-INVOLVED in additional services
  and/or organizations.  That is, always be certain that all understand
  that those activities are not part of your AC duties and that you can
  function as AC regardless of what transpires in the other circumstances.



Dissatisfaction with AC

       If you are dissatisfied with the performance of your AC, you should
  first discuss the matter with the AC.  It may be that the AC has tired
  of his duties, is experiencing problems that you are unaware of, or is
  actually doing better than you know.  In any case, the first step is to
  discuss the matter with the AC.  If it cannot be resolved in this
  fashion, then you should make the GC aware of the problem.  The GC
  should then check the matter with the AC.  If you have not made the AC
  aware of your concerns, that fact will come to light at that time.

       Through a process of communication among sysops, AC, and GC it is
  hoped that the matter can be resolved.  If not, the GC will discuss the
  matter with Wayne Bell who will have the final say in the matter.
  Communication, cooperation, and respect for one another are the keys to
  the successful resolution of problems.

       At the current time, there is no established procedure for the
  removal of an AC or a GC.  Each case, if it occurs, is handled on a
  case-by-case basis by Wayne Bell.  Discussions are underway regarding
  such procedures, so it is possible that a process will be adopted soon.



Sysops

       Sysops who decide to participate in WWIVnet should be aware that
  each host of a network sub has the right to insist upon her own rules,
  and she may delete any subscribing board that she wishes from the list
  of subscribers.  If the subscribing sysop does not like this, the only
  recourse is to start your own sub and/or convince the host to change her
  mind.  This is not an appropriate matter to raise with your AC, your GC,
  or Wayne Bell.  In this matter the host is Queen or King as the case may
  be.

       A Sysop should notify the host of any subs that he wishes to
  subscribe to and ask to be put on the distribution list for that sub.
  Doing so, means that the sysop is willing to adhere to the rules of that
  sub.  If the sysop later decides that he no longer wishes to take that
  sub, he should notify the host system.  Failure to notify the host
  system will result in that sub being sent to the subscriber anyway.
  Thus needless long distance costs are incurred by the systems carrying
  the mail.  Notifying the host of a desire to be dropped from a sub
  should be through netmail and not by a post on the sub.


       Sysops who receive subs from other systems have the responsibility
  to restrict access to the sub according to the rules of the host.  For
  example, some subs may limit access to User Number 1, to users with 255
  access, or some other requirements such as all posts must not have tag
  lines.  The receiving sysop must also take steps to inform users of the
  rules applying to a particular sub.  GFILES are often a good way of
  doing this.

       These guidelines for sysops are nothing more than common sense and
  normal courtesy which reflect the desire on the part of all to cooperate
  in order to make the network work properly and efficiently.  One of the
  interesting features of the network is that it is a great leveler.  No
  one (except possibly a few sysops) knows the age of the person making
  the post; therefore, people's impressions of the person who posts is
  made entirely based upon the language used and the thought expressed.
  As a consequence many a young user can convey the impression that he is
  much older and more mature, and some older users may convey the
  impression that they are irresponsible, illiterate users.  One hopes
  that users will opt to convey the impression that they are mature,
  responsible human beings.

       Sysops may choose to promote responsible use of the network by
  asking users to make their network posts conform to certain suggested
  guidelines.  For example, the Sysop may request that users:

       o    Not Use Foul language on the network
       o    Not make personal attacks against others
       o    Not post a lot of one-line messages on the network
       o    Learn the differences between using A, W, or P to respond to
            network messages.

       These are merely suggestions for responsible use of the network and
  are not requirements; however, some of those suggestions are also found
  in the rules of the hosts of many network subs.  Where they reflect the
  host rules, they are network rules for that sub.




Appendix C - Network Policy for Illegal Activities


  Mon Oct 15 20:39:31 1990
  RE: WWIVnet


  Nothing illegal (pirating, phreaking, hacking, bank robbing, etc) shall
  be sent over the net.  Violating this is cause for permanent removal
  from the network.  This has ALWAYS been the policy, I just felt I should
  re-iterate it, in case anyone has forgotten.  Now comes the new part:
  what happens locally on a system (that does not affect the network) is
  the business of that sysop, and is not an issue for the network.

  I am not advocating or approving of illegal acts.  I am merely stating
  that what a sysop has on his system is for him to decide.  As long as it
  does not affect the network, it is an issue only between that sysop and
  the police.  I am saying that AC's or GC's are not responsible for
  policing the systems.  That is a job for the police.  AC's and GC's are
  volunteer positions (ie, no pay), and I'm sure everyone has better
  things to do with their time than to go on a witch hunt for pirated
  files.

  $F4 1@1

  TOLERANCE

       Because communications are seldom perfect and because we, as human
  beings, are definitely less than perfect, it is likely that you may take
  offense at one time or another to something that is said in the network.
  If this happens, you should try to exercise tolerance toward others and
  their views and you should also exercise restraint when responding to
  others.  Although throwing out a few well-chosen expletives may make you
  feel much better, it seldom is the solution to a network problem.
  Instead, thoughtful, polite and courteous communication is more likely
  to sway the other person than vulgar shouting.  As a consequence, all
  who participate in the network are urged to exercise tolerance and
  restraint.



  LEAVING THE NETWORK

       If you decide to leave the network, you should notify your AC or GC
  at least three weeks in advance if possible.  You should also write e-
  mail to the host of each sub that you subscribe to and request that your
  node be deleted from his subscription list (Nxxxx.NET file).  If you
  host a sub, you might either make arrangements for someone else to take
  over being host and share your subscription list with that person so
  that the respective boards may be notified to change the host number in
  their NNxxxx.NET files, or you may notify each subscribing board that
  you are leaving the network and that no further messages will be
  forthcoming on SubType xxxx.  These simple courtesies are designed to
  help the network function more smoothly, to permit AC's and GC's to do
  their job appropriately, and to permit the hosts of subs to maintain
  accurate subscription lists.  While some people who are leaving the
  network have followed the procedure of posting a "goodbye" letter on
  each sub to which they subscribe, e-mail is a more effective method of
  accomplishing your purpose.  Some network hosts do not read all of the
  messages on the sub which they host and may easily miss a posted
  announcement whereas the receipt of e-mail is not as easily overlooked.


Appendix H - Procedure for Joining/Leaving WWIVnet:

  Procedure for joining WWIVnet:

  1. First, find out who your AC (or acting AC) is.

  (note: This section does not apply to WWCP sysops. The AC for all
  WWCP sites is 1@9702. You need to contact 1@9702 to join or leave
  the net.)

          a. If you already know some sysops in your area code, just ask
          one of them who your AC is.  If you don't know any other sysops
          in your area code, then, from any WWIVnet system, type "//net"
          from the main menu, and look for systems in your area code.
          Your AC will be the one identified by the '^' on his system's
          line of info.

          b. If there are WWIVnet systems in your area code, but there is
          no AC, then the GC for that area code is the acting AC.  There's
          no real easy way to find out who the GC is, from the net
          listing, so the easiest thing to do is to email one of the
          sysops in the area code, and ask them who the GC is.

          c. If there are no WWIVnet systems currently in your area code,
          then things become a bit more complicated.  You'll have to
          determine which system already in WWIVnet you'll be connecting
          with (through arrangements with that sysop).  You then need to
          ask that sysop who his GC is.  That person (his GC) is then your
          acting AC.


  2. Send email to your AC (or acting AC) (1@9702 for WWCP sites), through
  WWIVnet, to user #1 on the system (or in feedback on his system), telling
  the AC that you want to join WWIVnet.  The AC will need some specific
  information from you in order to process your request, so you should
  include that info in your original email, to avoid having to send email
  back and forth to the AC, in order for him to get the necessary info.
  Info you should include is:


          a. Info about your setup (system name, phone #, and modem info).
          Your system name should be 38 chars or less.  Your phone #
          should be in the standard AAA-PPP-####.  If you are outside the
          USA, and your phone # doesn't fit into that format, you'll have
          to make it fit.  Modem info you should include is your max baud
          rate, and protocols supported (if >2400 baud).  Specific modem
          protocols you should mention are: Telebit PEP, USR HST, Hayes
          V-series, V.32, V.32bis, and Compucom.

          b. How long your BBS has been up consistently (in months).

          c. Your WWIV registration number, or say you are not registered.

          d. If you have already arranged a connection with a system
          already in the network, mention that connection (by their
          WWIVnet node number).

  The text file "netapp.frm", included with the network .ZIP file, can be
  used to send this info.


  3. The AC (or acting AC) will then process your request.  The AC should
  have handled it within 2 weeks.  If it is not possible to handle it
  within 2 weeks, the AC will reply to you within the 2 week period
  indicating that it will take longer, approx how long it will take, and
  the reason(s) why.


  4. If everything goes well, the AC will respond within 2 weeks, telling
  you:

          a. Your WWIVnet node number.  You should enter this into the
          INIT program.

          b. If you did not specify a connection, the AC may suggest a
          connection for you.  Or, the AC may say that you'll have to find
          your own connection.

          c. Within a week or two after you've received your info from the
          AC, you should get added into the network, and start receiving
          mail.


  5. If everything doesn't go well:

          a. If the AC does not respond within 2 weeks, re-send your mail
          to him.  It's possible that the mail got lost, or that he's on
          vacation, or some other such thing.  If you don't get a reply 2
          weeks after that, then contact the GC, give him the same info
          you mailed the AC, plus the dates you sent the request to the
          AC, and say that you haven't yet received a reply.

          b. For some reason, the AC may determine that you cannot
          currently join the network.  In this case, the AC must reply to
          you giving the specific reason(s) why you are not being let into
          the network, and the circumstances (if any) under which you may
          be let into the network, in the future.  The AC will also send a
          copy of this letter to the GC.  If you think the reasons given
          are not legitimate, then you need to contact the GC, and explain
          your case to him.



  II. Leaving the network.

  1. You should notify your AC at least 3 weeks before you leave the
  network.  You should give as exact a date for your leaving as you can.
  Additionally, 2 weeks before you leave, remind your AC that you are
  leaving.


  2. About one week before you leave, your AC will remove all your
  connections except for one (you may specify which one is to be left).
  On about the date you specified (the next update after that date), the
  one remaining connection will be removed, and you will be dropped from
  the net data files.


  3. If some emergency arises outside your control, such that you are
  unable to give a 3 week warning, you should contact your AC as soon as
  possible, and inform him of the situation.

          a. For example, if your hard disk crashes, and you are unable to
          afford a new one, or your reserve unit is activated, and you
          have to leave for Saudi Arabia tomorrow, you should get ahold of
          your AC as soon as possible, so that you can be removed from the
          net data files, and cause as little disruption to the rest of
          the network as possible.

  4. If you have to leave the network without a 3 week warning, but it is
  NOT due to something outside your control (ie, you haven't been doing
  your homework, and your parents take away your computer), you should
  STILL notify your AC as soon as possible.  However, do not expect your
  AC or other sysops to be very happy with it.  Also, expect the AC to be
  very hesitant about letting you back into the network in the future.